Skip to content

Documentation - Github pages #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 8 commits into from

Conversation

gerazov
Copy link
Contributor

@gerazov gerazov commented Apr 23, 2022

I created a Read the Docs themed Sphinx version of the README and plugged it in to GitHub Pages. I've also added a Getting Started section as suggested in #183.

It looks really nice 😎 https://gerazov.github.io/orgmode/

I was following Continuous Documentation: Hosting Read the Docs on GitHub Pages up to the automation part.

The documentation in rst format is in ./docs_rst/ and the compiled website in ./docs - this is the only folder that can be specified other than root for gh-pages to work.

I've currently compiled the rst localjy to html using python-sphinx and make html, which generates the html in the ./docs_rst/_build/html/ folder. I then copied this to ./docs and activated gh-pages on the documentation branch and the ./docs folder.

I've done this manually just so I can share the way it looks. In the main repo it should be automated via scripts as described in Continuous Documentation: Hosting Read the Docs on GitHub Pages

@kristijanhusak
Copy link
Member

This looks great, thanks!

I would love to use a separate repo for this documentation, because having ~150 files in the main repo only for documentation seems a bit too much. Could you make a PR to a new repo that I just created? https://github.com/nvim-orgmode/docs

@gerazov
Copy link
Contributor Author

gerazov commented Apr 26, 2022

Ok I've moved the PR there nvim-orgmode/nvim-orgmode.github.io#1 👍

@gerazov gerazov closed this Apr 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants